home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 3.3 KB | 68 lines | [TEXT/GEOL] |
- Item 6268143 29-Dec-90 19:24GMT
-
- From: UK0392 EHN & DIJ Oakley,BDV
-
- To: MADA.SYSOP MacApp Dev Assoc, Don Sawtelle,IVC
-
- cc: MACAPP.TECH$ MacApp Technical
-
- Item forwarded by NEIL.RHODES to CALLIOPE
-
- ------------------------------------------------------------------------------
-
- Sub: Re Saving window posns
-
- [To DougAhmann on America Online]
-
- Doug & Friends,
-
- Yes, this is a problem, and I agree with your dislike of preferences files. We
- have apps which modify their own resources to save settings, and we also save
- some settings in the resource fork of the documents themselves. Although we are
- at odds with the trend in Apple, I would like to explain our rationale, as I
- think it saves our users a proliferation of bits and pieces accumulating in the
- System folder (yuck!).
-
- Those settings which are specific to a document - its own window size and
- position, any overridden default settings, and of course its own data - we save
- in the document file. For neatness’ sake, we put most of this stuff (apart from
- its data, of course) in the resource fork, just as MPW does for its documents.
-
- Those settings which are application defaults we save as resources within the
- resource fork of the application itself. OK, this means that each time they are
- changed, the app modification date changes - but of course, its creation date
- and version numbers stay the same, so our users soon get used to being able to
- read this information intelligently. Now, if we provide them with an update,
- they use a simple resource copying utility which we wrote, so that they can
- update the new version with their old defaults.
-
- This may seem elaborate, but our customers know that all they need to run our
- application is *one* file, the application itself (OK, we do have separate help
- files, but they can be over 1.5 Mbyte in size, and are only needed if they use
- online help, so I think that they can cope with this). If their Mac packs up
- (heaven forbid!), or they move the IIci onto the job and move the IIcx to
- another job, they move all the default settings in the *one* application file,
- and do not have to grovel around in the System folder.
-
- I accept that this may cause problems with some virus checkers - we use and
- recommend that *wonderful* program Disinfectant, with which this scheme has
- never clashed, so if it can cope, surely others can too?
-
- Our applications are used in the Apple-unfashionable production environments
- ('greasy Macs') of sailmaking lofts, light engineering factories, signmakers,
- tent and awnings makers, etc., by guys who want to get a job done simply and
- without fuss. They are *very* happy with this scheme, and we would not dare use
- Preferences files now, as their reaction would be most severe. Bear in mind
- also that if these guys use the wrong default setting (e.g. a scaling factor
- for the machinery we drive) they could ruin many tens of thousands of dollars
- worth of material.
-
- So, we would like an end to these nasty messy Preferences files in the System
- folder (I have a few whose original apps even now are unclear - how often do
- you have to clean defunct ones out of your System folder?), but to stick to the
- thoroughly proper use of resources in document and application files, and of
- course to the stationery files of System 7.
-
- Regards, Howard.
-
-